Systems and methods for resource utilization management

ABSTRACT

Systems and methods which provide resource utilization management, such as with respect to resources available through one or more accessible resource facilities, are disclosed. Embodiments provide resource utilization management systems and methods which facilitate user controlled reservation, access, and accounting for resource utilization. Resource utilization management systems of embodiments implement an electronic user key based infrastructure to enable access to and accounting for resources, such as resources of one or more accessible resource facility. Embodiments comprise unique tags for each resource for which resource utilization management is provided. A user device, such as a smart phone, personal digital assistant (PDA), or tablet computer, executing a resource utilization management application may be configured to provide a resource key device which is operable to scan the unique tag of a resource for accessing and relinquishing that resource, whether on an ad hoc and/or reservation basis.

TECHNICAL FIELD

The present invention relates generally to resource utilizationmanagement and, more particularly, to techniques for managing thereservation of, access to, accounting and/or payment for variousresources such as may be made available through one or more accessibleresource facility.

BACKGROUND OF THE INVENTION

A number of different space resources have been made available tovarious users in the past. Such space resources have included sharedspace resources which are accessible to a number of unaffiliated userssimultaneously and exclusive space resources which, although beingavailable for use by any number of unaffiliated users, are onlyaccessible to a particular user at any particular point in time.Management of the utilization of such resources has, however, not beenrobust.

For example, corporate and airline lounges provide shared spaceresources which have often been made available to users at locationsthroughout the world. However, the access to such shared spaces hastypically been membership based, whereby membership is required forentry into the lounge premises. A member user may thus presentcredentials to a receptionist or other gatekeeper and be permittedaccess to the lounge on an ad hoc basis. Once permitted access, the useris typically permitted complete access to the shared space facilities.Thus, the membership charges for access to the resource are generallybased upon a “one-size-fits-all” pricing model (e.g., an annualmembership fee, a monthly membership fee, or a daily access fee),typically determined based upon the average or expected utilization ofthe shared space resource and its amenities. Accordingly, although auser may be required to separately pay for certain items purchased at apoint of sale within the shared space resource (e.g., beverages or mealsconsumed by the user), a user is not enabled to pay for only thoseaspects of the shared space resource that the user actually availshim/herself of.

Although an operator of a shared space resource may be able to track auser entering the space, such as through the aforementioned presentationof credentials, the operator is often unable to track the user's exit.For example, the presentation of credentials for access is cumbersomeenough that user's will not tolerate a similar process upon departingthe space resource. Moreover, even when a user's entrance and exit ofthe space resource are captured, present solutions fail to provideinformation regarding the users' behavior within the space resource(e.g., the particular areas of the space which are utilized, theamenities the user does/does not avail themselves of, etc.).Accordingly, the operator of the space resource is provided with littleinformation regarding the actual use of the space resource and itsamenities by the users.

As another example, meeting rooms are often provided by hotels andairport fixed base operators (FBOs), whereby a user may have exclusiveaccess to the space resource for some period of time. The reservationand access process, however, is typically tedious and limited. Forexample, a user must often call and speak with a customer service agent,or engage in an email exchange, to determine the availability of thespace resource, provide payment information to reserve the space, andthen manually check in with a customer service agent, often againproviding the payment information, upon arrival at the space.

Although some providers of such exclusive access space resources haveprovided some level of automation for reserving a space resource, suchattempts are generally limited to a simple calendar for a particularspace resource showing its reserved/open times. The user may be enabledto select a time for their reservation and denote that on the calendar.However, if the desired time is not available the user must generallymanually select another space resource (if one is even offered) todetermine if the desired time is available. Moreover, the user of such aspace resource calendar must typically still manually check in with acustomer service agent upon arrival at the space.

Moreover, although a user may be provided exclusive use of the spaceresource, the user is nevertheless not charged only for theirutilization of that space resource. For example, a user is typicallycharged based upon their reservation of the space resource (e.g., anumber of hours or days that the user reserved the meeting room fortheir exclusive use), rather than the actual time that they availedthemselves of the space resource. Accordingly, if a user relinquishesthe space resource prior to the end of their reservation the user ischarged for the entire time of the reservation. This is often despiteanother user being ready and willing to utilize that space resource.This result may stem from the often cumbersome and generally slowprocess by which the utilization of the space resource is managed,whereby the first user's relinquishment of the space and the seconduser's desire to utilize the space are not able to be identified andconnected in time to facilitate the transition in use of the spaceresource.

Existing solutions have been unable to satisfactorily provide for ad hocutilization of exclusive space resources. That is, although shared spaceresources, wherein a large number of users are permitted tosimultaneously utilize the space resource, enable users to access thespace resource on an spontaneous, ad hoc basis, exclusive spaceresources are generally most effectively utilized via prior reservationof the space resource. For example, the process of determiningavailability of the space resource (e.g., due to upcoming reservationsby other users), blocking a time period for an ad hoc user, implementinga payment methodology, and granting physical access to the spaceresource often discourages many casual, ad hoc uses (e.g., spontaneoususes of an hour or less) of the space.

BRIEF SUMMARY OF THE INVENTION

The present invention is directed to systems and methods which provideresource utilization management, such as with respect to resourcesavailable through one or more accessible resource facility. Embodimentsof the invention facilitate the management of reservations, access,accounting and/or payment for various resources. The resources managedaccording to embodiments may comprise any number or combination ofshared resources, including shared space resources (e.g., lounges,libraries, gathering halls, common use areas, etc.), shared useresources (e.g., network printers, network scanners, network access,etc.), exclusive space resources (e.g., cubical, private offices,conference rooms, bathing facilities, etc.), and exclusive use resources(e.g., photocopiers, overhead projectors, video conference equipment,personal computing equipment, etc.).

Embodiments of the present invention provide resource utilizationmanagement systems and methods which facilitate user controlledreservation, access, and accounting for resource utilization. Thereservation functionality provided according to embodiments providesidentification of available resources meeting a user's needs or desires,including determining particular resources (such as by resource classand/or resource attributes) and times available to the user, and forestablishing ownership of the resources for a period of utilization bythe user. The access functionality provided according to embodimentsprovides user initiated access with respect to reserved resources aswell as ad hoc resource access. Such access may be provided with respectto free zones (e.g., zones for which no user fee is incurred) and/orpaid zones (e.g., zones for which a user fee is incurred). The accessfunctionality of embodiments provides for simultaneous access of aplurality of resources by a particular user, including nested resourceaccess (e.g., access to resources within resources) and parallelresource access (e.g., access to two or more separate resources), aswell as simultaneous access by a plurality of users. The accountingfunctionality provided according to embodiments provides for trackinguser's actual utilization of resources, including free zone resources,paid zone resources, shared space resources, shared use resources,exclusive space resource, exclusive use resources, and nested resources.Additionally or alternatively, the accounting functionality providedaccording to embodiments facilitates flexible, dynamic, and/or uniquepricing for resource utilization, such as based upon the particularresource, the particular user, the particular time of use, particularlocation of use, rewards based incentives, etc. Embodiments of theaccounting functionality provide for a single payment process upon auser exiting or otherwise relinquishing use of a last paid zone, such asa highest level paid zone resource (e.g., a first paid zoneaccessed/last paid zone relinquished, an outermost paid zone of a nestedgroup of paid zones accessed, or a paid zone providing a gateway betweenpaid zones and free zones), of a particular user experience.

Resource utilization management systems of embodiments of the presentinvention implement an electronic user key based infrastructure toenable access to and accounting for resources, such as resources of oneor more accessible resource facility. Embodiments comprise unique tags(e.g., quick response (QR) code tags, near-field communication (NFC)tags, radio frequency identification (RFID) tags, etc.) for eachresource for which resource utilization management is provided. A userdevice, such as a smart phone, personal digital assistant (PDA), ortablet computer, executing a resource utilization management applicationmay be configured to provide a resource key device which is operable toscan the unique tag of a resource for accessing and relinquishing thatresource, whether on an ad hoc and/or reservation basis. The user deviceand/or other user terminals (e.g., internet portal based user terminalinfrastructure) may be employed for reserving the resources, managing auser's account, etc., according to embodiments of the invention.Embodiments of a resource utilization management system infrastructureinclude a resource management backend platform, such as may comprise oneor more servers (e.g., a resource management server, a payment gatewayserver, etc.) operable to facilitate resource utilization managementoperation using the aforementioned user devices, user terminals, and thelike.

Operation of resource utilization management techniques of embodimentsherein not only facilitate highly accurate use based payment forresource utilization, but also facilitate robust management of theresources. For example, dynamic relinquishment of a resource by one userand use of the relinquished time for the resource by another user isfacilitated. Moreover, an operator of the resources is able to monitorthe users' actual use of particular resources, to thereby determineresources which should be increased to satisfy demand, resources to bedecreased due to insufficient demand, resources which are popular withusers and thus account for client satisfaction, etc. Additionally,transparency with respect to the costs incurred by users for their useof resources is provided, thus facilitating an understanding by users oftotal costs incurred, a view into the incremental cost associated withuse of particular resources, a value based resource utilizationanalysis, and the like.

The foregoing has outlined rather broadly the features and technicaladvantages of the present invention in order that the detaileddescription of the invention that follows may be better understood.Additional features and advantages of the invention will be describedhereinafter which form the subject of the claims of the invention. Itshould be appreciated by those skilled in the art that the conceptionand specific embodiment disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present invention. It should also be realized by thoseskilled in the art that such equivalent constructions do not depart fromthe spirit and scope of the invention as set forth in the appendedclaims. The novel features which are believed to be characteristic ofthe invention, both as to its organization and method of operation,together with further objects and advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. It is to be expressly understood, however, thateach of the figures is provided for the purpose of illustration anddescription only and is not intended as a definition of the limits ofthe present invention.

BRIEF DESCRIPTION OF THE DRAWING

For a more complete understanding of the present invention, reference isnow made to the following descriptions taken in conjunction with theaccompanying drawing, in which:

FIG. 1 shows an embodiment of a resource utilization management systemaccording to embodiments of the present invention;

FIG. 2 shows an embodiment of an accessible resource facility of aresource utilization management system according to embodiments of thepresent invention;

FIG. 3 shows interaction of a resource key device with other sub-systemsof a resource utilization management system according to embodiments ofthe present invention;

FIG. 4 shows a high level flow diagram showing user key-in/key-outoperation of a resource utilization management system according toembodiments of the present invention; and

FIG. 5 shows a high level flow diagram showing resource reservationoperation of a resource utilization management system according toembodiments of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows an embodiment of a resource utilization management systemaccording to embodiments of the present invention. Resource utilizationmanagement system 100 of FIG. 1 includes a plurality of accessibleresource facilities, shown as accessible resource facilities 110 a-110c, having resources available for use by users, the utilization of whichare managed according to the concepts herein. Users may interact withresource utilization management system via various means, such asresource key device 101 and/or user terminal 102. The users may comprisecasual users of the resources (e.g., users for which no preexistingcontractual or other commitment exists with respect to the user's accessto the resources made available by the resource utilization managementsystem) or member users of the resources (e.g., users for which someform of preexisting agreement for the user's access to the resourcesexists providing a contractual or commitment with respect to accessand/or payment for resource utilization, such as may include a monthlyor annual membership fee). Of course, there is no limitation withrespect to application of the concepts herein to member users payingmembership fees, and thus utilization of resources may be wholly userfee based, if desired. Where different kinds or classes of users aresupported, the fees incurred by such different users, including usebased resource user fees, may be different for the different kinds andclasses of users. Moreover, fees accounted for by resource utilizationmanagement systems of the present invention may be different on anindividual user by individual user basis, if desired.

The aforementioned user devices may comprise processor-based systemsoperable under control of instruction sets (e.g., software, firmware,applets, etc.) adapted to provide operation as described herein. Forexample, resource key device 101 may comprise a smart phone, a personaldigital assistant (PDA), a tablet device, a smart watch, and/or thelike, while user terminal 102 may comprise a notebook computer, apersonal computer, a browser based terminal, etc., all of which having aprocessor, memory, and input/output functionality operating undercontrol of an appropriate client application to provide the desiredfunctionality of concepts of the present invention. Resource key device101 of embodiments is preferably highly portable to facilitate userinteraction with resources as described herein, while user terminal 102may be less portable (or non-portable) according to some embodiments.

Embodiments of resource utilization management system 100 herein areadapted to operate across multiple user device platforms andmanufacturers. For example, through the use of resource key deviceapplications and the attendant functionality of resource utilizationmanagement system, users' smartphones may be adapted to be a key toaccess and reserve limited resources, as well as the ability to pay fortime of use of these resources. Such smartphones may include varioussensors (e.g., cameras, microphones, location, position, and/ororientation detection, etc.) which may be utilized according toembodiments. For example, most smartphones today have optical cameras(e.g., which may be in wider circulation than NFC enabled devices) whichmay be readily leveraged to sense/read resource tags and therebyfacilitate various aspects of resource utilization management asdescribed herein. The use of information as may be gathered using suchsensing of tags in combination with data on user and resource ID andclassification, time of use, price, period of use, and/or the othermetrics enable a platform of embodiments herein to manage resourceallocation, access, reservation, and payment, as described below withrespect to exemplary embodiments of the invention.

It should be appreciated, however, that embodiments herein are notlimited to smartphone based resource key devices nor to the use of anyparticular technology thereof. For example, a smartphone platform thatdoes not natively provide a particular feature, such as NFCcommunications, Bluetooth triangulation and tracking, etc., maynevertheless be provided with such technology (e.g., through the use ofa dongle coupled to a data port of the device, addition of a protective“sleeve” having the appropriate circuitry therein which couples to adata port of the device, etc.) where needed or desired for operation asa resource key device herein. Likewise, as different technologies (e.g.,NFC communications) become more widely adopted in particular user deviceplatforms, embodiments of a resource utilization management system mayleverage those technologies in addition to or in the alternative toother, legacy technologies.

Although embodiments of user devices are described above as comprisinggeneral purpose processor-based systems operable under control of aninstruction set to define operation in accordance with embodiments ofthe invention, user devices utilized according to the concepts hereinmay comprise special purpose devices. For example, resource key devicesof embodiments of the invention may comprise special purpose deviceshaving application specific integrated circuits (ASICs) and/orprogrammable gate arrays (PGAs) adapted to provide operation asdescribed herein.

Irrespective of the particular general purpose/special purpose nature ofuser devices herein, such resource key devices of the user devicespreferably include an interactive user interface and one or more scanneror sensor sub-system. For example, resource key device 101 may compriseuser output functionality (e.g., a display screen and/or audio output)to provide information regarding resources, resource availability,resource utilization, user account information, payment information,etc. Additionally, resource key device 101 may comprise user inputfunctionality (e.g., a touch screen, audio input, digital pointer,and/or keyboard) to accept input regarding resource selection, resourceaccess, resource utilization, user account information, paymentinformation, etc. Additionally or alternatively, resource key device 101of embodiments comprises one or more scanner sub-system (or sub-systemthat may be utilized in providing scanning according to embodimentsherein), such as may comprise a camera, a laser scanner, an opticalcircuit, a radio frequency (RF) transceiver (e.g., NFC communicationtransceiver), etc., operable to interact with tags associated withresources as described below.

It should be appreciated that operation of resource utilizationmanagement systems of embodiments herein may provide functionality inaddition to resource access, time of use accounting, and paymentmanagement. Accordingly, resource key devices of embodiments may beadapted to offer additional digital experiences (e.g., based on thelocation data the system has), such as to enable social networking inwhich users are enabled to make their location (e.g., resource oraddress they have provided) publicly known, to advertise their skills tothose in need on the network (e.g., such as design contractors oraccounts who can help growing businesses), etc.

The resources managed by a resource utilization management system ofembodiments of the invention may comprise various space resources,including shared space resources (e.g., lounges, libraries, gatheringhalls, common use areas, etc.) and/or exclusive space resources (e.g.,cubical, private offices, conference rooms, bathing facilities, etc.).Additionally or alternatively, the resources may comprise various useresources, including shared use resources (e.g., network printers,network scanners, network access, etc.) and/or exclusive use resources(e.g., photocopiers, overhead projectors, video conference equipment,personal computing equipment, etc.). Users may be provided access to anysuch resources according to embodiments, whereby such access maycomprise temporary “ownership” of the exclusive space and exclusive useresources exclusive of other users while such access may comprise jointuse of the shared space and shared use resource shared with other users.

FIG. 2 illustrates an exemplary embodiment of an accessible resourcefacility 110, such as may correspond to any of accessible resourcefacilities 110 a-110 c. Accessible resource facility 110 of theembodiment illustrated in FIG. 2 includes free zone 210 providing one ormore resource for which no user fees are incurred, although utilizationof such free zone resources may be monitored and/or managed according tothe concepts herein. Additionally, accessible resource facility 110 ofthe illustrated embodiment includes paid zone 220 providing one or moreresources for which user fees are incurred, whereby utilization of suchpaid zone are monitored and/or managed according to the concepts herein.

Free zone 210 illustrated in FIG. 2 includes lounge 211 comprising ashared space resource. For example, lounge 211 may comprise variousseating (e.g., sofas, club chairs, etc.) and/or working (e.g., tables,counters, etc.) areas available for shared use by a plurality of users.Free zone 210 may additionally or alternatively comprise a shared useresource, such as shared network access provided by WiFi service.Although not shown in the illustrated embodiment of free zone 210, oneor more exclusive space and/or use resource may be provided in a freezone according to embodiments of the invention.

Paid zone 220 illustrated in FIG. 2 includes library 221, comprising ashared space resource, and cubes 222 a-222 d and rooms 223 a-223 b,comprising exclusive space resources. For example, library 221 maycomprise various seating (e.g., sofas, club chairs, recliners, etc.)and/or working (e.g., desks, carrels, etc.) areas available for shareduse by a plurality of users. Library 221 may comprise amenitiesavailable for the users thereof, such as a collection of books (e.g.,reference books, novels, etc.), shared network access, and/or the like,at no additional user fee (i.e., the user fee associated with library221 includes access to such amenities). Cubes 222 a-222 d may compriseprivate or semi-private workspaces, such as may accommodate a smallcontingent of persons (e.g., 1-3 persons). For example, a cube providedaccording to embodiments may comprise an office type cubicle having awork surface, a telephone, computer network interface, electricaloutlets, etc., and seating for several individuals. Rooms 223 a-223 bmay comprise private meeting spaces, such as may accommodate a group ofpersons (e.g., 6-10 persons). For example, a room provided according toembodiments may comprise a conference room having a conference table andchairs, a podium, audio visual equipment, a telephone, teleconferenceequipment, etc.

Paid zone 220 of the illustrated embodiment includes shared useresources, shown as printer 225 and scanner 226, disposed in library221. These resources are available to users of library 221 in parallelwith their use of library 221 (i.e., a user fee for library 221 and auser fee for printer 225 and/or scanner 226 may be incurred/charged inparallel for the use thereof), according to embodiments.

Paid zone 220 of the illustrated embodiment includes exclusive spaceresources, shown as cubes 222 a-222 d and rooms 223 a-223 b, accessiblevia library 221. These resources are available to users of library 221as nested resources with respect to library 221 (i.e., a user fee forany of cubes 222 a-222 d and rooms 223 a-223 b will suspend the user feefor library 221 during use of the nested resource, while incurring theuser fee for utilization of the nested resource, such that the user feesare incurred/charged serially for the use thereof), according toembodiments.

It should be appreciated that the nesting of resources and/or theavailability of parallel resources may be provided in any level ofresource made available to users. For example, cubes 222 a-222 d androoms 223 a-223 b, which comprise a level of nested resources availablevia library 221, may themselves provide nested and/or parallelresources. The illustrated embodiment, for example, shows projector 224disposed within room 223 a providing an exclusive use resource availablein parallel with a user's utilization of room 223 a.

Each of the resources of the illustrated embodiment of accessibleresource facility 110 for which utilization management is provided byresource utilization management system 100 is provided a uniqueidentification tag, shown as tags 201 a-201 k. To facilitate utilizationmanagement according to embodiments herein, as will be better understoodfrom the description of embodiments which follows, a particular tag oftags 201 a-201 k is disposed on or near a corresponding one of theresources for which utilization management is provided. For example,tags 201 a-201 h are shown disposed near an entrance to an associatedspace resource (i.e., lounge 211, library 221, cubes 222 a-222 d, androoms 223 a-223 b, respectively), thereby facilitating interaction witha respective tag when access to an associated resource is desired.Similarly, tags 201 i-201 k are shown disposed on a surface of resources(i.e., projector 224, printer 225, and scanner 226, respectively),thereby facilitating interaction with a respective tag when access to anassociated resource is desired.

Although embodiments of tags, such as tags 201 a-201 k, may provideresource markers which are uniquely associated with a particularresource of a resource utilization management system, tags as usedherein may additionally or alternatively provide location markers. Everyresource within a particular location or sub-location may not beprovided with its own unique tag, but instead a tag may be provided fora location or sub-location which may be utilized with respect to anumber of resources associated with that location or sub-locationaccording to embodiments. For example, a seating arrangement availablefor use in a shared space, such as library 221, may comprise a table anda plurality of chairs. Such resources may be somewhat mercurial within aspace (e.g., moving within the space from time to time, increasing ordecreasing in exact number, etc.) and thus it may be cumbersome orotherwise problematic to assign and manage individual tags inassociation with each such resource. Rather than providing a tag foreach individual resource of this grouping, a single tag may be providedwith respect to the table to indicate use of the table and anunidentified one of the associated chairs. As an example of the use ofsuch location tag, a user may place an order for a consumable item(e.g., coffee or an office product), such as using a function ofresource key device 101, and scans a location tag to provide informationto accessible resource facility 110 as to the location of the user. Thisinformation may be utilized to confirm that the user is in fact in thefacility, to provide information regarding where the consumable item isto be delivered, etc.

Tags 201 a-201 k may comprise various means by which uniqueidentification of resources, and perhaps information associatedtherewith, may be provided according to the concepts herein. Forexample, any or all of tags 201 a-201 k may comprise quick response (QR)code tags, near-field communication (NFC) tags, radio frequencyidentification (RFID) tags, and/or the like, disposed on or near acorresponding resource. The tags utilized according to embodiments mayprovide unique identification of resources, wherein such uniqueidentification may not be unique in the universe but sufficiently uniqueto facilitate reliable identification of a particular resource withinresource utilization management system 100 for utilization management asdescribed herein. The tags may, for example, comprise a character string(e.g., alpha characters, numeric characters, or a combination thereof)uniquely identifying an associated resource (e.g., resource ID). Suchunique identification information may be utilized not only to uniquelyidentify a particular resource associated with the tag, but the uniqueidentification information may further be used to access additionalinformation (e.g., utilization pricing information, availabilityinformation, feature information, resource address and/or location,resource form, resource size and/or dimensions, resource function, etc.)for the resource. For example, the unique identification information maybe utilized in association with a relational database to retrieve suchadditional information. Additionally or alternatively, the informationprovided by tags of embodiments herein may comprise record locatorinformation, such as may identify a database record storing some or allof the foregoing information. Tags utilized according to embodiments ofthe invention may themselves store additional information, such as theaforementioned pricing information, feature information, resourcelocation, resource dimensions, etc.

Various items in addition to the foregoing tags may be associated withresources to facilitate utilization management according to embodimentsherein. For example, the embodiment of accessible resource facility 110illustrated in FIG. 2 includes information user interfaces (UIs) 202a-202 f provided in association with cubes 222 a-222 d and rooms 223a-223 b. Information Ins 202 a-202 f may comprise a display device(e.g., a processor-based display, a smart screen, a tablet device, etc.)adapted to interact with one or more sub-system of resource utilizationmanagement system 100 and receive current resource informationtherefrom.

Information UIs 202 a-202 f may provide display of information regardingan associated one of the resources. For example, an information UI mayprovide information regarding the features of the resource (e.g., theamenities of the resource, the nested or parallel resources associatedtherewith, etc.), the availability of the resource (e.g., a calendar oftimes the resource is reserved by users, the time of next availability),and/or the current status of the resource (e.g., in use or available).An information UI may additionally provide information regarding otherresources, such as to indicate a resource of a same or higher class isavailable when the resource associated with the information UI isunavailable. Such information regarding other resources may identify oneor more other resource, direct the user to the other resource(s), etc.It should be appreciated that information UIs of embodiments of theinvention may be interactive, such as to facilitate a user navigatingbetween desired portions of any or all of the aforementionedinformation.

Accessible resource facility 110 illustrated in FIG. 2 includes point ofsale 231 providing sale and/or distribution of various consumable items.For example, point of sale 231 may comprise a convenience store, acoffee shop, a lunch counter, an office supply store, and/or the likemaking various consumable items available to users of accessibleresource facility 110. Point of sale 231 of the illustrated embodimentis shown bridging both free zone 210 and paid zone 220, such as tofacilitate providing of consumable items to users of either or both suchzones. In operation according to embodiments of the invention, suchconsumable items may be provided on a per item/per unit purchase basiswith respect to users of free zone 210 and/or paid zone 220. However, aswill be appreciated from the description of embodiments below, differentprovision/purchase models may be enabled with respect to particularusers and/or users in different zones. For example, particularconsumable items may be provided for a charge to users in free zone 210while the same consumable items may be provided for a reduced charge orno charge (e.g., as an amenity of library 221) to users in paid zone220.

Although a particular configuration of accessible resource facility 110is illustrated in FIG. 2, it should be appreciated that he particularresources and/or the number of resources made available at anyparticular accessible resource facility may differ from those at otheraccessible resource facility. Accordingly, any or all of accessibleresource facilities 110 a-110 c may comprise a different configurationthan that of the exemplary embodiment shown in FIG. 2. Additionally, itshould be appreciated that, although three accessible resourcefacilities are illustrated in the exemplary embodiment of FIG. 1,embodiments herein may comprise any number of access resourcefacilities. Moreover, there is no limitation with respect to theresources for which utilization management is provided be associatedwith an accessible resource facility. Various resources may, forexample, be made available and utilized independent of an accessibleresource facility and any other resources, if desired.

The resources made available through accessible resource facilities 110a-110 c include shared resources (e.g., shared space resources, such aslounge 211 and library 221, and shared use resources, such as printer225 and scanner 226) which are accessible to a number of unaffiliatedusers simultaneously and exclusive resources (e.g., exclusive spaceresources, such as cubes 222 a-222 d and rooms 223 a-223 b, andexclusive use resources, such as projector 224) which, although beingavailable for use by any number of unaffiliated users, are onlyaccessible to a particular user at any particular point in time.Accordingly, embodiments of resource utilization management system 100of FIG. 1 are adapted to facilitate the management of reservations,access, accounting and/or payment for various resources availablethrough accessible resource facilities 110 a-110 c.

Referring again to FIG. 1, resource utilization management system 100includes resource server 120 and payment gateway 130 cooperativelyoperable with respect to resources of accessible resource facilities 110a-110 c to provide for user controlled reservation, access, andaccounting for utilization of the resources. Resource server 120 andpayment gateway 130 may comprise processor-based systems, such asgeneral purpose processor-based computers having memory and input/outputfunctionality operable under control of one or more instruction sets toprovide operation as described herein. For example, resource server 120and/or payment gateway 130 may comprise one or more web server (e.g., asingle web server configured as virtual machines for the resource serverand the payment gateway, a resource server web server and a paymentgateway web server, a server farm for either or both the resource serverand payment gateway, etc.) operable to provide the functionality ofembodiments described herein. Resource server 120 and/or payment gateway130 may comprise one or more database useful in operation according toembodiments herein. For example, resource server 120 may comprise anaccessible resource facility database providing information regardingthe accessibility resource facilities of the resource utilizationmanagement system, a resource database providing information regardingthe resources of the resource utilization management system (e.g., theresources of each accessible resource facility), a database of users ofthe resource utilization management facility, and/or the like. Suchdatabases may be maintained to include dynamically updated information,such as regarding the use and availability of resources, user access toand utilization of resources, user preferences regarding resources andpayment, etc. Resource server 120 and/or payment gateway 130 may, forexample, comprise user account information database providinginformation regarding user accounts and rates, user payment informationproviding information regarding methods of payment and paymentaccounting, payment processing information providing information forprocessing payments, etc.

Resource server 120 and payment gateway 130 may be providedcommunication via network 150 with various user devices, such asresource key device 101 and/or user terminal 102, accessible resourcefacilities, such as accessible resource facilities 110 a-110 c, and/orresources, such as resources 211, 221, 222 a-222 d, 223 a-223 b, and/or224-226, for operation as described herein. Network 150 may comprisevarious networks capable of data communication, such as the publicswitched telephone network (PSTN), the Internet, an intranet, anextranet, a local area network (LAN), a metropolitan area network (MAN),a wide area network (WAN), a cable transmission network, a cellularcommunication network, and/or the like, for providing communication tofacilitate functionality as described herein.

Reservation functionality is provided by resource server 120 of resourceutilization management system 100 according to embodiments, whereby auser may identify available resources of accessible resource facilities110 a-110 c meeting a user's needs or desires, including determiningparticular resources (such as by resource class and/or resourceattributes) and times available to the user, and for establishingownership of the resources for a period of utilization by the user. Forexample, a user may utilize either or both of resource key device 101and user terminal 102 to interface with resource server 120 and reserveresources, obtain reports regarding reserved resources, determine theavailability of resources for reserving, modify or cancel resourcereservations, and/or the like.

Access functionality is provided by resource server 120 of resourceutilization management system 100 according to embodiments, whereby auser initiates access with respect to reserved resources and/or ad hocresource access using the aforementioned tags. For example, a user mayutilize resource key device 101 of embodiments to interact with anappropriate tag of tags 201 a-201 k to access an associated resource ofresources 211, 221, 222 a-222 d, 223 a-223 b, and 224-226. As shown inthe illustration of FIG. 3, the user may operate resource key device 101to scan a particular tag 201 and obtain the information thereof. Thisinformation may be processed by resource key device 101 and/orcommunicated to resource server 120 (e.g., the scanned informationcommunicated to resource server 120, information resulting fromprocessing of the scanned information by resource key device 101communicated to resource server 120, or a combination thereof) to accessthe associated resource. Information in addition to the aforementionedscanned information and/or information resulting from processing of thescanned information may be communicated by resource key device 101 toresource server 120 according to embodiments herein. For example,resource key device 101 may provide information regarding the user'sidentity or user's account to resource server 120 for facilitatingoperation as described herein.

The foregoing access functionality may provide for simultaneous accessof a plurality of resources by a particular user. For example, a usermay be provided parallel resource access, wherein the user is providedaccess to two or more separate resources, whereby such parallel resourceaccess may be in addition to nested resource access, wherein the user isprovided access to resources within resources (e.g., parallel resourcesmay be provided within a nested relationship with another resource).Moreover, the foregoing access functionality may provide forsimultaneous access to various resources by a plurality of users.

Accounting functionality is provided by resource server 120 and paymentgateway 130 of resource management system 100 according to embodiments,whereby resource server 120 provides for tracking user's actualutilization of resources and payment gateway 130 provides paymentaccounting and payment processing. For example, resource server 120 mayprovide detailed resource utilization data to payment gateway 120 foruse by gateway 120 in invoice generation, billing, payment collection,and/or payment processing. As shown in the illustration of FIG. 3, auser may utilize resource key device 101 of embodiments to interact withresource server 120 to confirm resource utilization details and,thereafter, interact with payment gateway 130 to initiate payment forthe resource utilization. Payment gateway 130 of embodiments operates tointerface with one or more payment processing system (e.g., paymentprocessing facility 140), such as may comprise an automated clearinghouse (ACH) facility, an electronic check conversion service, a creditcard processing facility, and/or the like, to facilitate payment for theresource utilization. Embodiments of the invention provide for theforegoing cooperative operation of resource server 120 and paymentgateway 130 to implement a single payment process upon a user exiting orotherwise relinquishing use of a last paid zone resource, such as ahighest level paid zone resource (e.g., a first paid zone accessed/lastpaid zone relinquished, an outermost paid zone of a nested group of paidzones accessed, or a paid zone providing a gateway between paid zonesand free zones), of a particular user experience (e.g., upon a userexiting paid zone 220 of accessible resource facility 110 of FIG. 2).

As will be better understood from the discussion which follows, theinteraction between resource server 120 and payment gateway 130 ofembodiments is not limited to the reporting of resource utilization byresource server 120 and the resulting generation of an invoice orstatement by payment gateway 130. For example, the accountingfunctionality provided according to embodiments facilitates flexible,dynamic, and/or unique pricing for resource utilization, such as basedupon the particular resource, the particular user, the particular timeof use, particular location of use, rewards based incentives, etc.Accordingly, payment gateway 130 may comprise a database of user accountinformation, including resource pricing for particular users, rewardmilestones for particular users, etc., such as may be reported bypayment gateway 130 to resource server 120 for facilitating variousfunctionality according to embodiments. For example, resource server 120may provide information regarding the cost for utilization of aparticular resource to a user, such as in response to a user a userinitiating access with respect to a resource using the aforementioneduser key device and tags in order to confirm that the user agrees toincur the particular charges.

Having described components of a resource utilization management systemadapted according to embodiments of the invention, attention is directedto FIG. 4 wherein a high level flow diagram showing operation of such aresource utilization management system is provided in flow 400. Inparticular, flow 400 shows the process for a user keying in or out of aresource, such as any of resources 211, 221, 222 a-222 d, 223 a-223 b,and 224-226, using resource key device 101 according to embodiments ofthe present disclosure.

At block 401 of the illustrated embodiment, the user initiates a key-inor key-out interaction with a particular resource. It should beappreciated that such a subject resource for which the key-ininteraction is initiated may comprise a resource for which the user hasreserved, a priori, access privileges for the resource or may comprise aresource for which the user wishes to access on an ad hoc basis.

In key-in and key-out interactions according to embodiments of operationat block 401, the user may manipulate resource key device 101 (e.g.,manipulate a resource key device button or touch screen, shake aresource key device having motion sensing capability, provide a voicecommand to an audio input of the resource key device, hold the resourcekey device in proximity to a resource tag, place the resource key devicein contact with a resource tag (such as to tap or bump the resourcetag), etc.) to indicate that the user wishes to make a request withrespect to a resource, thereby causing the resource key device ofembodiments to initiate a request in the form of a user report (referredto herein as a U-report). In response to the user initiating therequest, the resource key device may operate to scan a tag associatedwith a resource which the user wishes to access. For example, if theuser wishes to access lounge 211 (part of free zone 210), the user maymanipulate resource key device 101 to scan tag 201 a, disposed near anentry of lounge 211 in the embodiment illustrated in FIG. 2. Similarly,if the user wishes to access library 221 (part of paid zone 220), theuser may manipulate resource key device 101 to scan tag 201 b disposednear an entry of lounge 211 in the illustrated embodiment. If the userwishes to room 223 a (part of paid zone 220 nested within library 221)or the access projector 224 (part of paid zone 220 available in parallelwith room 223 a) the user may manipulate resource key device 101 to scana respective one of tags 201 g (disposed near an entry of room 223 a inthe illustrated embodiment) or 201 i (disposed on a surface of projector224 in the illustrated embodiment).

Manipulation of resource key device 101 to scan a tag may comprisevarious actions and interactions, depending upon the particularconfiguration of resource key device and tags used. For example, wherethe resource key device comprises a smart phone and the tag comprises aQR code tag, manipulation of the resource key device may compriselaunching a resource utilization management system client app, selectinga QR code tag scan function, and causing a camera of the smart phone tocapture an image of the appropriate QR code tag for processing. Wherethe resource key device comprises a RFID reader (e.g., a smart phone, adedicated purpose device, or other device adapted to have RFID scanningfunctionality), manipulation of the resource key device may compriselaunching a resource utilization management system client app, selectinga RFID tag scan function, and ensuring that the resource key device iswithin proximity of the appropriate RFID tag for RF interrogation andprocessing of the interrogated information. Where the resource keydevice comprises a NFC reader (e.g., a smart phone, a dedicated purposedevice, or other device adapted to have NFC scanning functionality),manipulation of the resource key device may comprise launching aresource utilization management system client app, selecting a NFC tagscan function, and touching the resource key device to, or perhapsplacing the resource key device nearby, the appropriate NFC tag fornear-field interrogation and processing of the interrogated information.

Irrespective of the particular technique used for scanning the tag,operation at block 401 of flow 400 according to embodiments processesthe information obtained from the scanned tag to generate a resourcequery report (referred to herein as a Q-report) for furtherkey-in/key-out processing with respect to the associated resource. AQ-report preferably contains information uniquely identifying theassociated resource or from which the resource may be uniquelyidentified. Additionally, the Q-report may include additionalinformation, such as information regarding the class of the particularresource (e.g., lounge, library, cube, room, printer, scanner,projector, etc.), the location of the resource (e.g., physical address,the particular accessible resource facility, the floor within theaccessible resource facility, the zone in which the resource isdisposed, etc.), and/or information associated with the uniqueness ofthe key-in/key-out event. It should be appreciated that some or all ofthe foregoing information may be encoded in the tag (e.g., obtained bythe resource key device by scanning the tag) or may be accessibleexternal to the tag (e.g., stored in a database of the resource keydevice or the resource server and accessed using information obtained byscanning the tag). Accordingly, generation of the Q-report ofembodiments herein may comprise utilizing information obtained from thescanned tag to access additional information, perhaps throughcommunication with resource server 120, used in the Q-report.Alternatively, however, the Q-report of embodiments may comprise aunique resource identifier which, when utilized by the resource server,provides any necessary information for the particular resource.

Operation for key-in or key-out at block 401 of flow 400 of embodimentsfurther includes generation of a device report (referred to herein as aD-report). For example, Q-report generation as described above promptsoperation by resource key device 101 to generate a D-report utilizedwith respect to accessing resources herein. A D-report preferablycontains information identifying a user account associated with theresource key device initiating the key-in/key-out process (e.g.,identifying the particular resource utilization management system useror client that is engaging in the key process). The D-report may includeadditional information, such as a timestamp at which this event hasoccurred and/or other information from or associated with the particularkey event. For example, information obtained from one or more sensor(e.g., camera, microphone, thermometer, positioning sensor, etc.) may becollected and included in the D-report for use by a resource serverherein. A camera, or other light sensor, may capture the ambient lightlevel, for use in making adjustments to lighting within space of theresource for which the user wishes to utilize, for instance.Additionally or alternatively, information regarding various preferences(e.g., room temperature, lighting level, audio and/or video programmingselections, etc.) of the user regarding their preferred experience withthe resource, the class of resource in which the resource is included,or the resources which the user may access may be included in a D-reportaccording to embodiments of the invention. Such information may, forexample, be utilized by a resource server in configuring a resource forthe user, in addition to granting access/ownership of the resource tothe user and providing accounting functionality as described herein.

In operation of the user key-in/key-out process at block 401 ofembodiments, the information above, or some portion thereof, is utilizedin making a request to resource server 120. For example, the foregoingU-report, Q-report, and D-report, or some portion(s) thereof, may beused to compile an aggregated access request report (referred to hereinas a UQD-report) which is provided to resource server 120 with respectto the user accessing the resource by resource key device 101, such asvia network 150. Such an access request may thus provide identificationof the resource that the user is making a request with respect to andmay include additional information useful for the user's accessexperience (e.g., the above described information regarding location andclass of the resource, the user's preferences, etc.).

At block 402 of flow 400 a determination is made as to whether aresource identified in an access request (e.g., the aforementionedUQD-report) is available. In operation according to embodiments,resource server 120 may utilize information from the access request toidentify the resource that the user is accessing (e.g., using resourceidentification information from the access request, using information inthe access request to obtain resource identification information from adatabase available to the resource server, etc.) and to determine thestate of the resource (e.g., using resource identification informationto access a resource database storing utilization state information). Aswill be more fully described below, a resource may be available to theuser, already in use by the user, or the resource may be unavailable tothe user (e.g., a shared resource is in use by a capacity number ofusers already or an exclusive resource is in use by another user).

Accordingly, resource server 120 may operate to determine if the subjectresource is currently in an “available” state or an “unavailable” state.Where the resource is indicated as being in an available state (e.g.,using a resource information database available to resource server 120),the resource may be determined to be available to the user. In contrast,where the resource is indicated as being in an unavailable state (e.g.,using the resource information database), the resource may be determinedto be unavailable to the user. However, where the resource is indicatedas being in a reserved state (e.g., using the resource informationdatabase), further processing may be performed to determine if the useris the one for whom the reservation is made. If the resource reservationis for the user, the resource may be determined to be available to theuser. However, if the resource reservation is for another user, theresource may be determined to be unavailable to the user.

In operation according to embodiments, a report regarding theavailability state of the resource is provided in response to the accessrequest at block 402. For example, resource server 120 may provide anaffirmative report (referred to herein as a Y-report) or a negativereport (referred to herein as a N-report) regarding the availabilitystate of the resource to resource key device 101 for further processingaccording to flow 400 of the illustrated embodiment. As will be betterunderstood from the discussion which follows, such Y-reports andN-reports may include various information (e.g., resource information,user preference information, pricing information, access timeinformation, information regarding other resources, such as alternativeresources, nested resources, parallel resources, etc.) to facilitateoperation as described herein. It should be appreciated that theaforementioned information may include globally applicable information(e.g., availability and/or pricing information applicable to all usersof the resource utilization management system), information applicableto a subset of users (e.g., availability and/or pricing informationapplicable to a member/non-member user, applicable to a particular levelof user, etc.), information applicable to particular users (e.g.,availability and/or pricing information applicable to an individualuser), and the like.

Assuming that it is determined that the resource is available at block402, processing according to the illustrated embodiment proceeds toblock 403 wherein an affirmative report is provided. For example,resource server 120 may provide a Y-report to resource key device 101,such as via network 150, to indicate that the subject resource isavailable to the user.

Having been provided an affirmative report with respect to the resource,processing according to the illustrated embodiment proceeds to block 404for user confirmation of the desire to access the subject resource. Forexample, resource key device 101, upon receiving a Y-report in responseto an UQD-report, may display a query to the user to ask the user toconfirm that the user wishes to access the resource, requiring aresponse from the user (e.g., manipulation of a resource key devicebutton or touch screen, shaking of a resource key device having motionsensing capability, a voice response to an audio input of the resourcekey device, etc.) to assent to the resource access. It should beappreciated that such a user confirmation may be utilized to provide a“two-tap” configuration according to embodiments in which the userperforms a first “tap” when affirmatively manipulating the resource keydevice to initiate the key-in/key-out process (e.g., scan a particularresource tag) and then a second “tap” when affirmatively manipulatingthe resource key device to confirm the desire to utilize the resource.Such a two-tap configuration may be desirable for use with respect topay per use resources to avoid disputes or confusion with respect tocharges incurred by a user, to avoid undesired or unintended grants ofaccess (e.g., associated with accidental interaction of a resource keydevice with a resource tag), etc.

The aforementioned user confirmation, in addition to providing theaforementioned “two-tap” confirmation, may be utilized to presentinformation to the user regarding the resource and receiveacknowledgment of the information by the user. For example, theaffirmative report may include various information regarding the subjectresource, such as pricing information for the use of the resource asapplicable to the user (e.g., global pricing information where suchpricing is applicable to the user, group pricing information where theuser is a member of a particular group of users, or individual pricinginformation when such pricing is applicable to the user), informationregarding a default time the user will be granted access, informationregarding a period of time the resource is available for the user,information regarding amenities of the resource, nested or parallelresources available with respect to the user's utilization of theresource, rewards/loyalty points awarded for use of the resource,rewards/loyalty points available for redemption toward use of theresource, and/or the like, which may be presented to the user by theresource key device in a user confirmation process according toembodiments. For example, a price per hour/price per unit and/or totalcost of utilization of the resource may be presented to the user inassociation with a query for the user's confirmation that the resourceis to be accessed by the user, thereby providing affirmativeconfirmation with respect to the charges to be incurred by the user.Similarly, a default time (e.g., 15 minutes) for the user's access tothe resource may be presented to the user for confirmation and/or userselection of a different time (e.g., increase/decrease the default time,perhaps in predetermined increments of time).

Although the foregoing description of resource availability andconfirmation has been with reference to a resource that is the subjectof a user's key-in/key-out interaction, it should be appreciated thatoperation may additionally provide such functionality with respect toadditional resources. For example, the subject resource (e.g., room 223a of FIG. 2) may include a nested resource (e.g., projector 224) and/orhave one or more resources commonly used in parallel with the subjectresource (e.g., printer 225 and scanner 226). Resource server 120 ofembodiments may identify such additional resources (e.g., throughinteraction with a resource information database, analysis of pastusers' utilization of the resources, analysis of the requesting user'sutilization of resources, analysis of the user's preference information,etc.) and include information (e.g., availability, pricing, etc.)regarding one or more such additional resource in the Y-report.Operation by resource key device 101 of embodiments may thus presentinformation regarding these additional resource(s) to the user forconfirmation at block 404 to allow the user to not only confirm that thesubject resource is to be accessed, but to also access one or moreadditional resource. The user may select/confirm or not select/notconfirm any such resource for access by the user. Alternatively, the usemay provide preference information indicating that the user wouldlike/not like access to additional resources (e.g., particularadditional resources, additional resources typically available withrespect to particular subject resources, particular classes ofresources, etc.) to thereby automatically select one or more additionalresource or avoid being provided with the opportunity to select one ormore resource, as desired. It should be appreciated, however, that morethan one resource, and in particular more than a particular resourceinitially identified by the user in a user key-in/key-out operation maybe provided access through a same key-in/key-out operation ofembodiments herein.

As previously discussed, operation at block 404 of the illustratedembodiment provides for user confirmation of the desire to access thesubject resource. In operation according to the illustrated embodiment,should the user respond to the confirmation in the negative (i.e.,indicate that access to the subject resource is not desired) or fail torespond to the confirmation in the affirmative (i.e., indicate thataccess to the subject resource is desired) within some predeterminedperiod of time (e.g., confirmation time-out threshold) the user will notbe provided access to the resource and processing proceeds to block 410where the key-in/key-out process of the illustrated embodimentterminates. Such operation provides for avoiding accidental or unwantedgrants of access to resources, thereby preventing disputed chargesincurred by the user, unnecessary unavailability of resources to otherusers, etc. Accordingly, embodiments preferably implement theaforementioned user confirmation processing, or some other form ofaccess confirmation. It should be appreciated, however, that theaforementioned user confirmation process may be omitted according toembodiments, if desired.

Should the user respond to the confirmation at block 404 in theaffirmative (i.e., indicate that access to the subject resource isdesired), processing according to the illustrated embodiment proceeds toblock 405 wherein user access to the subject resource is initiated. Forexample, resource key device 101 may provide a Y-report to resourceserver 120 indicating the user's confirmation of the subject resource(and perhaps additional resource(s)) access. The user may thus utilizethe resource. For example, where the resource is a space resource (e.g.,lounge 211, library 221, cubes 222 a-222 d, or rooms 223 a-223 b), theuser may enter and enjoy the space, and amenities thereof, initiateaccess with respect to nested and/or parallel resources associatedtherewith, etc. Where the resource is a use resource (e.g., projector224, printer 225, or scanner 226), the user may begin utilizing of theresource.

In operation according to embodiments, upon initiation of user accessto/ownership of the subject resource, resource server 120 records theuser's access, such as for various purposes including accounting,loyalty point award, resource utilization tracking, establishing andmonitoring user resource access/ownership time periods, and/or the like.For example, where the subject resource is an exclusive resource, theresource may be designated as “in-use” by resource server 120, therebyproviding “ownership” of the resource to the user and making theresource unavailable to other users. Where the subject resource is ashared resource, a utilization count may be incremented for use indetermining when the utilization of the shared resource has reachedcapacity (e.g., where capacity may be an issue with respect toadditional users being granted access to the resource). Resource server120 may additionally or alternatively initiate a timer or otherutilization tracking functionality, such as may be useful in determiningcharges for the resource utilization by the user, for initiatingcontinued utilization confirmation messaging to the user, for resourceutilization management, tracking, and/or planning purposes, etc. Itshould be appreciated that even where the subject resource is part offree zone 210 of the embodiment illustrated in FIG. 2, such utilizationcount and timer information may be desirable, such as to manage theresources made available at an accessible resource facility, to ensure acapacity limit (e.g., fire code occupancy limit) is not exceeded, toaward loyalty points, to provide periodic messaging to confirm that auser has not relinquished access without initiating a key-out process,and/or the like.

Initiation of user access to/ownership of the subject resource maycomprise various control and/or messaging operations. For example,resource server 120 may provide a message to resource key device 101indicating that the access has been granted, providing a timer or piececounter for indicating access remaining to the user, providing a runningcharge tally for indicating the charges incurred by the user inreal-time, etc. Such control or messaging may be provided to devicesand/or subsystems in addition to or in the alternative to theaforementioned resource key device. For example, resource server 120 mayprovide control signals to the subject resource itself, or somesubsystem thereof, to facilitate access and/or use by the user. As oneexample, resource server 120 may cause a bolt to release to physicallygrant access to a space resource. Additionally or alternatively,resource server 120 may control a state (e.g., power-on or active state)of lighting and/or amenities (e.g., audio system, television, telephonesystem, climate control system, etc.) within a space resource to enableutilization by the user and/or to set operation thereof at userpreference levels. Similarly, resource server 120 may control a state(e.g., power-on or active state) of a use resource to facilitate itsutilization by the user. As another example, resource server 120 mayprovide control and/or messaging signals to one or more information UI(e.g., an information UI of information UIs 202 a-202 f associated withthe subject resource) to control display of the “in-use” status of theresource, the time the resource is to again become available for use, atime or piece utilization counter, etc. It should be appreciated thatthe control of such an information UI to display the in-use status of anassociated resource, according to embodiments, facilitates an “honor”system for use of resources (e.g., avoiding the use of bolts, powerdisruption, etc. to prevent unauthorized use of a resource by clearlydisplaying the in-use/available state of a resource thereby discouragingtrespassing), self-service, ad hoc access to resources by the users, andgeneral transparency with respect to the use and enjoyment of resourcesof the resource utilization management system.

After processing to initiate user access to/ownership of the subjectresource, operation according to the illustrated embodiment proceeds toblock 406 wherein an access period is monitored. For example, resourceserver 120 may operate an access timer/piece counter throughout theuser's utilization of the resource for accounting, tracking, and/ormanagement purposes. Where the user is provided some predeterminedaccess period or piece count, processing according to embodiments mayoperate to monitor the appropriate timer/counter to determine if theaccess period is expired. Even where the user is not provided somepredetermined access period or piece count, monitoring a timer/counterto initiate periodic queries to the user to confirm their continueddesire to utilize the resource and that they have not relinquishedaccess to the resource without a key-out process may be desired. If theaccess period has not expired, processing at block 406 may loop tocontinue monitoring for expiration of the access period. However, if theaccess period has expired, processing according to the illustratedembodiment proceeds to block 407.

At block 407 of flow 400 of FIG. 4, resource relinquishment processingis initiated. For example, resource server 120 may generate an exitreport (referred to herein as an E-report) for facilitating gracefultermination of the user's access to the subject resource. An E-reportmay, for example, include information regarding the expiration of a timeperiod or piece count of the user's access, the charges incurred, thefurther availability of the resource for access by the user, otherresources available to the user, etc. Such an E-report may be providedby resource server 120 to resource key device 101 for resourcerelinquishment confirmation and/or other exit processing operation.

Having been provided exit processing information, such as theaforementioned E-report, processing according to the illustratedembodiment proceeds to block 408 for user confirmation of the desire torelinquish access to the subject resource. For example, resource keydevice 101 may, upon receiving an E-report, display a message to theuser regarding a time or piece count threshold having been met and toquery to the user to ask the user to confirm that the user wishes torelinquish access to the resource. In operation according toembodiments, a response is solicited from the user (e.g., manipulationof a resource key device button or touch screen, shaking of a resourcekey device having motion sensing capability, a voice response to anaudio input of the resource key device, etc.) to avoid accidently orunintentionally relinquishing the resource access. If, for example, theuser either fails to respond to the query or responds to the query inthe affirmative (i.e., indicating assent to relinquishment of theresource access), processing according to the illustrated embodimentproceeds to block 409 for resource access exit processing.

The resource access exit processing provided at block 409 of embodimentsmay include accounting and/or payment processing. For example, resourceserver 120 may operate to stop a timer/piece counter and determine atotal charge incurred by the user's utilization of the resource beingrelinquished. This information may be provided to the resource keydevice for display to the user and/or for use in other processingaccording to embodiments herein. For example, resource server 120 maygenerate an accounting report (referred to herein as an A-report)comprising information such as that described above and provide thatreport to resource key device 101, such as via network 150. Preferredembodiments operate to provide for invoicing and payment for resourceutilization at the conclusion of a user's experience or paid resourceexperience (e.g., upon the user exiting the accessible resource facilityor upon the user exiting the paid zone of the accessible resourcefacility). Accordingly, where the user is relinquishing access to anested resource or a parallel resource and continuing to access anotherresource (e.g., a higher level resource, such as a paid resource throughwhich access was gained to the resource for which access is beingrelinquished or an outer paid resource of a nested group of paidresources in which the resource for which access is being relinquishedis part of, or another resource used in parallel with the resource forwhich access is being relinquished), processing at block 409 for exitingthis particular resource may not result in payment processing (e.g., theuser may be advised of the costs incurred, without yet being presentedwith an invoice or a solicitation for payment). The user, nevertheless,accrues the charges for the resource exited (assuming the resource was apaid resource) and may continue to accrue charges for one or moreresources (e.g., a higher level resource into which the user exits, oneor more parallel resources still being accessed by the user, etc.),according to embodiments of the invention. It should be appreciated thatresource server 120 of embodiments may continue to operate one or moretimer and/or piece counter (e.g., as appropriate to resources for whichthe user continues to access), perhaps at rates different than thoseassociated with the utilization of the resource exited, after resourceaccess exit processing of block 409 where the user continues to accessresources of the accessible resource facility.

It should be appreciated from the foregoing that operation of a resourceutilization management system of embodiments may provide tracking withrespect to the utilization of individual resources by the user (e.g.,for accounting purposes, resource availability purposes, reward/loyaltypurposes, etc.), tracking of the user throughout an accessible resourcefacility (e.g., for facility management purposes, for user experiencemonitoring purposes, etc.), and accounting and payment processing (e.g.,for applying appropriate usage fees on a user by user and resource byresource basis, for automated invoicing and payment collection, etc.).Such operation facilitates the management of resources to ensure anappropriate number of resources are made available (e.g., to attempt toalways have particular resources available for ad hoc access by userswhile maintaining a level of resource utilization to keep the businessviable), to enable an enhanced user experience (e.g., allowing ad hocaccess, reserved access, unassisted and unilateral interaction withresources by users, etc.), and/or to make a plurality of resourcesreadily available for use by users (e.g., subscribing or member users,casual or walk-up users, etc.).

Operation at block 409 may include processing in addition to theaforementioned accounting and/or payment processing. For example,resource server 120 may update the status of the exited resource to“available” in a resource database. Additionally or alternatively,resource server 120 may provide control and/or message signaling, suchas to update one or more information UI (e.g., an information UI ofinformation UIs 202 a-202 f associated with the subject resource) tocontrol display of the “available” status of the resource, to provide amessage to a resource key device of another user that the resource hasbecome available, etc. In operation according to embodiments, suchsignaling may operate to control a state (e.g., power-off or standbystate) of lighting and/or amenities (e.g., audio system, television,telephone system, climate control system, etc.) within a space resourceand/or control a state (e.g., power-off or standby state) of a useresource to set operation thereof at default or standby levels.

Upon completion of the resource access exit processing provided at block409, operation the process for a user keying in or out of a resource offlow 400 of the illustrated embodiment terminates at block 410. Itshould be appreciated that, although this particular process hasterminated with respect to a particular user's key-in/key-out process,the process may continue to be implemented with respect to this user(e.g., for a higher level resource of a nested set of resources) and/orother users of the resource utilization management system.

Referring again to the determination made at block 408, if, rather thanresponding to the query in the affirmative or failing to respond to thequery at all, the user instead responds to the query in the negative(i.e., indicating a desire not to relinquish the resource access),processing according to the illustrated embodiment returns to block 402wherein a determination is made as to whether the subject resource isavailable for the user's further use. Further processing as describedherein with respect to the resource availability determination andproviding user access or reporting resource unavailability may thus beprovided.

Having described processing according to flow 400 for the situationwhere a subject resource is determined to be available in response to auser key-in operation according to the embodiment illustrated in FIG. 4,reference is again made to the determination made at block 402. If,rather than it being determined that the resource is available at block402, it is determined that the resource is unavailable to the requestinguser (e.g., due the resource being “owned” by another user whether byreservation or access, the resource being at capacity through use byother users, etc.), processing according to the illustrated embodimentproceeds to block 411 for resource unavailability processing.

At block 411 of embodiments, a negative report is provided. For example,resource server 120 may provide a N-report to resource key device 101,such as via network 150, to indicate that the subject resource isunavailable to the user. Such a N-report may include various information(e.g., resource information, resource access availability information,pricing information, information regarding other resources, such asalternative resources, nested resources, parallel resources, etc.) tofacilitate operation as described herein.

Having been provided a negative report with respect to the subjectresource, processing according to the illustrated embodiment proceeds toblock 412 for user selection of a different, available resource and/or adifferent, available time. For example, resource key device 101, uponreceiving a N-report in response to an UQD-report, may displayinformation regarding availability of one or more other resource, one ormore time the subject resource or another resource is available, etc.For example, where the subject resource is currently not available, butis scheduled to become available in the near future (e.g., 15-45minutes), such information may be provided in the N-report and resourcekey device 101 may display a message to inform the user accordingly.Additionally or alternatively, information regarding alternativeresources (e.g., resources of a same class, a similar class, having thesame or similar features, nearby in proximity, etc.) which areavailable, or which are scheduled to become available in the nearfuture, may likewise be provided in the N-report and correspondingly amessage displayed to the user regarding their availability. Theinformation regarding such alternative resources (the alternativeresources including an alternative available time for the subjectresource) provided to the user may include information in addition toidentification of the particular alternative resources available.

Operation at block 411 according to embodiments, having been presentedwith alternative resource availability information, as described above,may proceed to query the user regarding whether the user wishes toaccess one or more of the alternative resources. For example, the usermay be enabled to select a particular alternative resource/time (e.g.,through manipulation of a resource key device button or touch screen, avoice response to an audio input of the resource key device, etc.) toselect a desired alternative resources. Where the user elects to accessan alternate resource, processing according to the illustratedembodiment proceeds to return to block 402 wherein this resource isavailability is confirmed and remains available for the user. Furtherprocessing as described herein with respect to the resource availabilitydetermination and providing user access or reporting resourceunavailability may thus be provided. Where the user elects to access analternate time, processing according to the illustrated embodimentproceeds to initiate a resource reservation process, as represented byblock 413 (an example of which is described below with respect to flow500 of FIG. 5), in order to establish “ownership” of the appropriateresource at an alternate time. However, where the user does not elect toaccess an alternate resource/time, processing according to theillustrated embodiment proceeds to block 410 where the key-in/key-outprocess of the illustrated embodiment terminates.

Having described processing according to flow 400 for the situationswhere a subject resource is determined to be available or unavailable inresponse to a user key-in operation according to the embodimentillustrated in FIG. 4, reference is again made to the determination madeat block 402. If it is determined that the user already has “ownership”of the subject resource (e.g., the user has already been granted accessto the resource), operation according to the illustrated embodimentoperates under the presumption that the user may wish to relinquishaccess to that resource and thus proceeds to block 414. That is, inoperation according to embodiments, a same tag may be used with respectto a resource for both a key-in and key-out process to thereby provide asimple, intuitive user interface. Accordingly, where it is determined atblock 402 that the user already has access to the subject resource,processing is provided according to embodiments to determine if the userwishes to relinquish access to that resource.

At block 414 of flow 400 of FIG. 4, resource relinquishment processingis initiated. For example, resource server 120 may generate an E-reportfor facilitating termination of the user's access to the subjectresource. An E-report may, for example, include information regardingthe expiration of a time period or piece count of the user's access, thecharges incurred, the further availability of the resource for access bythe user, other resources available to the user, etc. Such an E-reportmay be provided by resource server 120 to resource key device 101 forresource relinquishment confirmation and/or other exit processingoperation.

Having been provided exit processing information, such as theaforementioned E-report, processing according to the illustratedembodiment proceeds to block 415 for user confirmation of the desire torelinquish access to the subject resource. For example, resource keydevice 101 may, upon receiving an E-report, display a message to theuser regarding the user already having access to the subject resourceand to query to the user to ask the user to confirm that the user wishesto relinquish access to the resource. In operation according toembodiments, a response is solicited from the user (e.g., manipulationof a resource key device button or touch screen, shaking of a resourcekey device having motion sensing capability, a voice response to anaudio input of the resource key device, etc.) to avoid accidently orunintentionally relinquishing the resource access. If, for example, theuser either fails to respond to the query or responds to the query inthe negative (i.e., indicating the user does not wish to relinquishaccess to the resource), processing according to the illustratedembodiment returns to block 406 wherein the user continues to haveaccess to the subject resource and an access period is continued to bemonitored. However, if the user responds to the query in the affirmative(i.e., indicating assent to relinquishment of the resource access),processing according to the illustrated embodiment proceeds to block 409for resource access exit processing, as described above.

It should be appreciated from the foregoing that exiting a resource mayrelinquish access to that resource and stop accrual of charges (wherethe resource is a paid resource) associated with the use thereof. Suchexiting a resource may not, however, stop accrual of all charges for theuser. For example, the user may exit a nested resource and thus the userstatus may automatically revert into the next higher level nestedresource (e.g., a resource that is outside of the resource that is beingexited). A specific example of this may be that the user exits cube 222a and thus is automatically switched back to library 221. As library 221is also part of paid zone 220, thus having a paid aspect thereof, theuser may continue to accrue charges (although perhaps at a differentprice/rate etc.) for utilization of resources after having relinquishedaccess to cube 222 a. Stated another way, the key-out process withrespect to one resource (e.g., cube 222 a) may simultaneously provide akey-in process with respect to another resource (e.g., library 221). Itshould be appreciated, however, that such simultaneous key-out/key-inprocessing need not be implemented according to embodiments, such aswhere resources are utilized in parallel rather than nested. In aparallel resource utilization scenario, the user may key-in/key-out ofthe parallel resources independently, for example.

It should also be appreciated that a user need not continue to accruecharges after having relinquished access to a resource. For example,where the user relinquishes access to all resources of a paid zone(e.g., exits library 221 of paid zone 220), the accrual of charges withrespect to that user may cease. The user may, nevertheless,simultaneously key-in to another resource. For example, the key-outprocess with respect to library 221, and thus paid zone 220, maysimultaneously provide a key-in process for lounge 211, and thus freezone 210. Although charges may not accrue to a user with respect totheir use of resources of a free zone, embodiments of the invention maynevertheless provide management and/or tracking with respect to a user'saccess to such resources (e.g., to collect data regarding theutilization of resources, to provide access management for capacitylimitations, to provide particular amenities for certain users/classesof users, to award loyalty points, etc.). Embodiments may, however, notimplement key-in and/or key-out processes with respect to certainresources, such as the aforementioned free zone resources, such as whereresource tracking, data collection for the utilization of theseresources, etc. is not desired.

Embodiments may provide resource access exit processing, such as throughoperation at block 409 of embodiments, which facilitates a key-out ofall resources (or perhaps all paid zone resources) in a same operation.For example, a “checkout of all resources” option may be provided to auser for initiating key-out processing as described herein with respectto all resources (or all paid zone resources) currently being accessedby a user. Such a feature may be utilized to ensure that a user does notincur charges, or that resources are not otherwise shown as beingutilized by the user, when the user does not intend to utilize theresources further. Where the user has accessed a number of resources,perhaps including a number of nested resources and/or parallelresources, such an option to checkout of all resources may be desirableto provide comfort to the user that the resource utilization managementsystem is properly updated to reflect the user's relinquishment of allresources.

Resource access exit processing provided at block 409 of embodiments mayinclude payment processing, such as to invoice and/or collect for theutilization of the resource being exited and possibly other resourcesutilized by the user during their experience. For example, embodimentsherein may operate to provide for invoicing and payment for resourceutilization at the conclusion of a user's experience or paid resourceexperience (e.g., upon the user exiting the accessible resource facilityor upon the user exiting the paid zone of the accessible resourcefacility). Accordingly, where the user is relinquishing access to anested resource or a parallel resource and continuing to access anotherresource (e.g., a higher level resource), processing at block 409 forexiting this particular resource may not result in payment processing(e.g., the user may be advised of the costs incurred, without yet beingpresented with an invoice or a solicitation for payment). However, wherethe user is relinquishing access to a highest level resource of a paidzone (e.g., library 221 of paid zone 220) or otherwise exiting a paidzone, processing at block 409 may result in payment processing for allthe resources utilized during the user's experience. As another example,where the user is relinquishing access to a last resource of anaccessible resource facility, whether in a paid zone or free zone,(e.g., lounge 211 of accessible resource facility 110) or otherwiseending their current experience, processing at block 409 may result inpayment processing for all the resources utilized during the user'sexperience. Of course, embodiments may operate to provide paymentprocessing at other times, such as upon exit/relinquishment of any paidzone resource, periodically (e.g., daily, weekly, monthly, yearly,etc.), etc., as desired.

Payment processing according to embodiments may comprise presentinginformation regarding the user's utilization of resources, solicit theuser's confirmation of the charges, collect payment information and/orauthorization, submit a payment transfer request, and/or the like. Forexample, resource server 120 may compile information regarding theutilization of resources by the user (e.g., particular resourcesutilized, times/duration of utilization, etc.). Using such utilizationinformation, resource server 120 may access a user account informationdatabase providing information regarding user accounts and rates togenerate a report or invoice for the resource utilization. Such a reportmay be provided to the user for review and acceptance and/or to paymentgateway 130 for submission of a payment transfer request. Paymentgateway 130 may, for example, access a user account information databaseproviding information user payment information providing informationregarding methods of payment and payment accounting, payment processinginformation providing information for processing payments, etc. andinteract with an appropriate payment processing facility (e.g., paymentprocessing facility 140) to request transfer of funds in payment for theuser's utilization of resources. Payment gateway 130 of embodiments maythus interface into an ecommerce platform (e.g., infrastructure providedby an ecommerce service provider, such as BRAINTREE) for facilitatingpayment fulfilment.

Although the foregoing payment processing has been described withrespect to the user's utilization of resources, it should be appreciatedthat such payment processing may be provided with respect to the saleand/or distribution of various consumable items in association withpoint of sale 231. For example, the user's acquisition of variousconsumable items from point of sale 231 may be tracked by resourceserver 120, as discussed above with respect to the utilization ofresources, and thus included in a resource utilization report andpayment fulfillment at block 409 of embodiments. Alternatively, paymentprocessing with respect to such consumable items may be provided at thepoint of sale (e.g., as the consumable items are obtained by the user),using processing by resource server 120 and/or payment gateway 130 asdescribed above.

It should be appreciated that, although the foregoing operation of aresource utilization management system for a user (e.g., “member” user)keying in or out of a resource has been described with reference to auser's own use of the resource(s), embodiments may provide resourceaccess with respect to one or more other users, such as by or on behalfof a member user. For example, a member user (e.g., a user having thecapability and/or authority to himself/herself directly andindependently access managed resources of an accessible resourcefacility) may invite another user (e.g., “guest” user) to either accessthe resource in accompaniment of the member user or perhaps in themember user's stead. In accordance with embodiments, such a member usermay, when accessing a resource, when reserving a resource, etc.,designate that a guest user is to have access to the resource, perhapsproviding identification information of the guest user. The member usermay, in operation according to embodiments, be charged for the guestuser's utilization of the resource(s), such as at a highest levelresource rate for the guest user's access. The guest user of embodimentsmay not have a resource key device, and thus may rely upon the memberuser to key the guest user in and/or out of the resource(s). Forexample, the member user's resource key device may include a selection(e.g., software enabled button) to check their guest into and out of anyresources when the member user accesses or relinquishes the resource(s).Additionally or alternatively, the guest user may be provided a resourcekey device (e.g., through downloading an applet on the gust user's smartphone or other processor-based device), or perhaps a limited functionresource key device such as may be tied to the member user's accountand/or resource key device, to facilitate the guest user keying inand/or out of resource(s) designated by the member user.

Having described operation of a resource utilization management systemof embodiments herein with respect to a user keying in or out of aresource, reference is now made to FIG. 5 wherein a high level flowdiagram showing operation of a resource reservation process of aresource utilization management system is provided in flow 500. Theresource reservation process of flow 500 may, for example, be utilizedto reserve one or more resources in advance to thereby provide“ownership” and ensure availability of the resource to the reservinguser. For example, a user may access the resource reservation processremotely with respect to the resource(s) being reserved (e.g., when notpresent at a resource location, such as accessible resource facility110), such as through interaction of resource key device 101 and/or userterminal 102 with resource server 120 via network 150. Additionally oralternatively, a user may access the resource reservation processlocally with respect to the resource(s) being reserved (e.g., whenattempting to access a resource currently in use by another user andthus reserving the resource at a later time, when wishing to reserve aresource for future use, etc.), such as through interaction of resourcekey device 101 with resource server 120 and/or user terminal 102 vianetwork 150.

At block 501 a resource calendar, or other resource availabilityinformation resource, is accessed for use in determining theavailability of one or more resource. For example, a resource databaseproviding information regarding the resources of the resourceutilization management system, accessible to resource server 120, maystore information regarding the current and planned (e.g., reserved)utilization of various resources. This information may be organized intoa calendar format, or other suitable format, for presentation to a userfor identifying one or more resources and available time meeting theuser's need or desires.

In operation, a user may identify a particular resource the user wishesto reserve access for and availability information for that particularresource may be accessed and a resource availability calendar generated.Additionally or alternatively, a user may identify a class of resources,particular attributes or amenities desired with respect to a resource, aparticular location for a resource, etc. and availability informationfor one or more resources meeting or most nearly meeting the identifiedinformation may be accessed and a resource availability calendargenerated. It should be appreciated that a particular resource, or evenresources in a class of resources, identified by a user may not beavailable at a time or within a time window desired by the user,accordingly embodiments of the invention herein may operate to provideavailability information with respect to alternative resources (e.g.,other resources available at a desired time, at a desired location,having one or more attribute meeting that indicated by the user, etc.).

At block 502 of the illustrated embodiment, having been provided withresource availability information, the user indicates a selection of aresource the user wishes to reserve for their later use. Such selectionof a resource may comprise identifying the particular resource orperhaps designating a class of resources for which one or more resourcesmeeting the user's needs are available. Such selection of a resource mayfurther include a desired time window for the use of the resource (e.g.,a date and particular time of day, such as may include a starting timeand ending time or starting time and length of use period, for thereservation). Additional information may also be provided by the user toaid in establishing a reservation of resources suitable to the user. Forexample, the user may identify particular nested resources or resourceamenities that the user wishes to be available to the user during theproposed reservation.

It should be appreciated that, in the situation where the user isattempting ad hoc access to a resource that is already in use orreserved by another user, operation of the resource reservation processmay be provided for facilitating reserving of the resource (or anotherresource), such as at a later time. Accordingly, resource selection atblock 502 of embodiments may, for example, comprise the user selectingan alternative time for the particular resource for which the ad hocaccess had been attempted. For example, the resource calendarinformation accessed at block 501 may provide the user with theavailable times of the resource for the user to select a time (e.g., anext available time) for their use of the resource. Additionally oralternatively, resource selection operation at block 502 may utilizeinformation regarding resource availability accessed at block 501 toprovide the user with the ability to select another (e.g., alternative)resource, such as a same or similar resource having immediateavailability or availability sooner than the resource for which ad hocaccess was attempted.

Processing according to the illustrated embodiment of flow 500 thenproceeds to block 503 wherein a determination with respect to theavailability of the particular resource, or a resource meeting theuser's selections, is made. In operation according to embodiments,resource server 120 may utilize information from the user's selection atblock 502 to identify a resource that the user has selected forreserving and to determine the state of the resource (e.g., usingresource identification information to access a resource databasestoring utilization state information). As will be more fully describedbelow, a resource may be available to the user, already reserved by theuser, or the resource may be unavailable to the user (e.g., a sharedresource reserved by a capacity number of users already or an exclusiveresource reserved by another user).

Accordingly, resource server 120 may operate to determine if the subjectresource is currently in an “available” state or an “unavailable” state.Where the resource is indicated as being in an available state for theproposed reservation period (e.g., using a resource information databaseavailable to resource server 120), the resource may be determined to beavailable to the user. In contrast, where the resource is indicated asbeing in an unavailable state for the proposed reservation period (e.g.,using the resource information database), the resource may be determinedto be unavailable to the user. If, for example, the resource is reservedfor another user during the proposed reservation period, the resourcemay be determined to be unavailable to the user. However, where theresource is indicated as already being reserved to the user for theproposed reservation period (e.g., using the resource informationdatabase), further processing may be performed to determine if the userwishes to alter or cancel the reservation.

In operation according to embodiments, a report regarding theavailability state of the resource is provided in response to theresource reservation selection at block 503. For example, resourceserver 120 may provide an affirmative report (e.g., the aforementionedY-report), a negative report (e.g., the aforementioned N-report), or anexit report (e.g., the aforementioned E-report) regarding theavailability state of the resource, such as to resource key device 101or user terminal 102, for further processing according to flow 500 ofthe illustrated embodiment.

Assuming that it is determined that the resource is available for theproposed reservation period at block 503, processing according to theillustrated embodiment proceeds to block 504 wherein an affirmativereport is provided. For example, resource server 120 may provide aY-report to resource key device 101 or user terminal 102, such as vianetwork 150, to indicate that the subject resource is available to theuser for the proposed reservation period.

Having been provided an affirmative report with respect to the resource,processing according to the illustrated embodiment proceeds to block 505for user confirmation of the desire to reserve the resource for theproposed reservation period. For example, resource key device 101 oruser terminal 102 may, upon receiving a Y-report in response to theresource reservation selection, display a query to the user to ask theuser to confirm that the user wishes to reserve the resource for theproposed reservation period, requiring a response from the user (e.g.,manipulation of a resource key device button or touch screen, shaking ofa resource key device having motion sensing capability, a voice responseto an audio input of the resource key device, etc.) to assent to theresource reservation.

The aforementioned user confirmation, in addition to providing theaforementioned “two-tap” confirmation, may be utilized to presentinformation to the user regarding the resource and receiveacknowledgment of the information by the user. For example, theaffirmative report may include various information regarding theresource reservation, such as pricing information for the use of theresource as applicable to the user (e.g., global pricing informationwhere such pricing is applicable to the user, group pricing informationwhere the user is a member of a particular group of users, or individualpricing information when such pricing is applicable to the user),information regarding modification or cancellation of the resourcereservation, information regarding amenities of the resource, nested orparallel resources available with respect to the reserved resource,rewards/loyalty points to be awarded for use of the resource,rewards/loyalty points available for redemption toward use of theresource, and/or the like, which may be presented to the user by theresource key device or other user terminal in a user confirmationprocess according to embodiments. Where, for example, a user has notdesignated a ending time for the reservation or has otherwise notindicated a reservation period (e.g., the user may have indicated astarting time but not an ending time for the reservation) theaforementioned additional information may include a default time (e.g.,15 minutes) for the user's reservation of the resource. This informationmay be presented to the user for confirmation and/or user selection of adifferent time (e.g., increase/decrease the default time, perhaps inpredetermined increments of time).

As previously discussed, operation at block 505 of the illustratedembodiment provides for user confirmation of the desire to reserveresource. In operation according to the illustrated embodiment, shouldthe user respond to the confirmation in the negative (i.e., indicatethat reservation of the resource is not desired) or fail to respond tothe confirmation in the affirmative (i.e., indicate that reservation ofthe resource is desired) within some predetermined period of time (e.g.,confirmation time-out threshold) the reservation of the resource to theuser will not be made and processing proceeds to block 507 where theresource reservation process of the illustrated embodiment terminates.Such operation provides for avoiding accidental or unwanted reservationof resources. Accordingly, embodiments preferably implement theaforementioned user confirmation processing, or some other form ofreservation confirmation. It should be appreciated, however, that theaforementioned user confirmation process may be omitted or differentthan that shown, according to embodiments. For example, a user mayrespond to the confirmation in the negative (i.e., decline the resourcereservation) not because the user does not wish to reserve the resource,but because some aspect of the resource reservation offered forconfirmation is not suitable to the user (e.g., a default reservationperiod is insufficient for the user's needs). Accordingly, rather thanproceeding to block 507 to end the resource reservation process,embodiments may query the user as to whether the proposed reservationshould be altered, whereby an affirmative response may repeat theresource reservation process or some portion thereof (e.g., returning toblock 501) and a negative response may proceed to block 507 to end theresource reservation process.

Should the user respond to the confirmation at block 505 in theaffirmative (i.e., indicate that reservation of the resource isdesired), processing according to the illustrated embodiment proceeds toblock 506 wherein resource reservation processing is performed. Forexample, resource key device 101 or user terminal 102 may provide aY-report to resource server 120 indicating the user's confirmation ofthe resource reservation. Resource server 120 may then update the stateof the resource for the reservation period (e.g., using resourceidentification information to access a resource database storingutilization state information) to reflect the reservation. Likewise,resource server 120 may update information of a user account informationdatabase to reflect the reservation.

Resource reservation processing may comprise various control and/ormessaging operations. For example, resource server 120 may provide amessage to resource key device 101 and/or user terminal 102 indicatingthat the resource reservation has been granted, providing cancellationpolicy information, etc. Such control or messaging may be provided todevices and/or subsystems in addition to or in the alternative to theaforementioned resource key device and other user terminals. Forexample, resource server 120 may provide control signals to the subjectresource itself, or some subsystem thereof, to facilitate access and/oruse by the user during the reservation period. As another example,resource server 120 may provide control and/or messaging signals to oneor more information UI (e.g., an information UI of information UIs 202a-202 f associated with the reserved resource) to control display of the“reserved” status of the resource, the time period of the reservation,etc. It should be appreciated that the control of such an information UIto display such information regarding the resource reservation, as wellas the in-use status information discussed above, facilitates ad hocaccess to the resource by the users of the resource utilizationmanagement system, as well as general transparency with respect to theuse and enjoyment of resources of the resource utilization managementsystem.

Having described processing according to flow 500 for the situationwhere a resource is determined to be available in response to a userresource reservation operation according to the embodiment illustratedin FIG. 5, reference is again made to the determination made at block503. If, rather than it being determined that the resource is availableat block 503, it is determined that the resource is unavailable to therequesting user (e.g., due the resource being “owned” by another user,the resource being at capacity through reservation by other users,etc.), processing according to the illustrated embodiment proceeds toblock 508 for resource unavailability processing.

At block 508 of embodiments, a negative report is provided. For example,resource server 120 may provide a N-report to resource key device 101 oruser terminal 102, such as via network 150, to indicate that theresource is unavailable for reservation to the user. Such a N-report mayinclude various information (e.g., resource information, resource accessavailability information, pricing information, information regardingother resources, such as alternative resources, nested resources,parallel resources, etc.) to facilitate operation as described herein.

Having been provided a negative report with respect to the resource,processing according to the illustrated embodiment proceeds to block 509for user selection of a different resource and/or a different, availabletime. For example, resource key device 101 or user terminal 102 may,upon receiving a N-report in response to a resource reservationselection, display information regarding availability of one or moreother resource, one or more time the subject resource or anotherresource is available, etc. Additionally or alternatively, informationregarding alternative resources (e.g., resources of a same class, asimilar class, having the same or similar features, nearby in proximity,etc.) which are available during the proposed reservation period, orwhich are scheduled to become available near the proposed reservationperiod, may likewise be provided in the N-report and correspondingly amessage displayed to the user regarding their availability. Theinformation regarding such alternative resources (the alternativeresources including an alternative available time for the subjectresource) provided to the user may include information in addition toidentification of the particular alternative resources available.

Operation at block 509 according to embodiments, having been presentedwith alternative resource availability information, as described above,may proceed to query the user regarding whether the user wishes toperform resource reservation processing with respect to one or more ofthe alternatives. For example, the user may be enabled to select aparticular alternative resource/time (e.g., through manipulation of aresource key device button or touch screen, a voice response to an audioinput of the resource key device, etc.) to select a desired alternativeresources. Where the user elects to perform resource reservationprocessing with respect to an alternative, processing according to theillustrated embodiment proceeds to return to block 503 wherein thisresource is availability is confirmed and remains available for theuser. Further processing as described herein with respect to theresource reservation may thus be provided. However, where the user doesnot elect to perform resource reservation processing with respect to analternative resource/time, processing according to the illustratedembodiment proceeds to block 507 where the resource reservation processof the illustrated embodiment terminates.

Having described processing according to flow 500 for the situationswhere a resource is determined to be available or unavailable inresponse to a user resource reservation operation according to theembodiment illustrated in FIG. 5, reference is again made to thedetermination made at block 503. If it is determined that the user hasalready reserved the resource for the reservation period, operationaccording to the illustrated embodiment operates under the presumptionthat the user may wish to relinquish the reservation of that resource ormodify that resource reservation in some way and thus proceeds to block510.

At block 510 of flow 500 of FIG. 5, resource reservationrelinquishment/modification processing is initiated. For example,resource server 120 may generate a reservation report for facilitatingcancellation of the user's resource reservation or the user'smodification of the resource reservation. Such a reservation report may,for example, include information regarding the resource reserved, theperiod of the reservation, the cost for utilization of the resourceduring the reservation period, amenities and/or other resourcesavailable with respect to the resource of the resource reservation, thefurther availability of the resource for reserving by the user, etc. Areservation report may be provided by resource server 120 to resourcekey device 101 and/or user terminal 102 for resource reservationrelinquishment/modification confirmation and/or other resourcereservation processing operation.

Having been provided resource reservation information, processingaccording to the illustrated embodiment proceeds to block 511 for userconfirmation of the desire to relinquish the reservation or to indicatea desire to modify the reservation. For example, resource key device 101or user terminal 102 may, upon receiving a reservation-report, display amessage to the user regarding the user already having a reservation withrespect to the subject resource and to query to the user regardingwhether the user would like to relinquish the resource reservation or ifthe user would like to modify the resource reservation. In operationaccording to embodiments, a response is solicited from the user (e.g.,manipulation of a resource key device button or touch screen, shaking ofa resource key device having motion sensing capability, a voice responseto an audio input of the resource key device, etc.) to avoid accidentlyor unintentionally relinquishing the resource reservation.

If, for example, the user either fails to respond to the query orresponds to the query in the negative (i.e., indicating the user doesnot wish to relinquish or modify the resource reservation), processingaccording to the illustrated embodiment proceeds to block 507 whereinwhere the resource reservation process of the illustrated embodimentterminates (i.e., the existing resource reservation remains unchanged).For example, resource key device 101 or user terminal 102 may provide aN-report to resource server 120 indicating the user's desire to continueto hold the resource reservation.

If, at block 511, the user responds to the query in the affirmative withrespect to relinquishing the resource reservation (i.e., indicatingassent to relinquishment of the resource reservation), processingaccording to the illustrated embodiment proceeds to block 506 forresource reservation processing, as described above. For example,resource key device 101 or user terminal 102 may provide a Y-report toresource server 120 indicating the user's confirmation of resourcereservation cancellation. Resource server 120 may then update the stateof the resource for the reservation period (e.g., using resourceidentification information to access a resource database storingutilization state information) to reflect the reservation having beencancelled and the resource thus being available. Likewise, resourceserver 120 may update information of a user account information databaseto reflect the reservation cancellation.

It should be appreciated that the resource reservation processingprovided in association with relinquishing a resource reservation maycomprise various control and/or messaging operations. For example,resource server 120 may provide a message to resource key device 101and/or user terminal 102 indicating that the resource reservation hasbeen cancelled, providing cancellation fee information whereappropriate, etc. Such control or messaging may be provided to devicesand/or subsystems, such as to one or more information UI (e.g., aninformation UI of information UIs 202 a-202 f associated with thereserved resource) to control display of the “reserved” status of theresource to reflect the cancellation of the reservation and theavailability of the resource, etc.

If, however, the user responds to the query in the affirmative withrespect to modifying the resource reservation (i.e., indicating a desireto modify the resource reservation in some regard) at block 511,processing according to the illustrated embodiment proceeds to block 512for resource reservation modification processing. For example, resourcekey device 101 or user terminal 102 may provide a Y-report to resourceserver 120 indicating the user's confirmation of resource reservationmodification. Resource reservation modification processing at block 512operates to obtain information regarding one or more aspect of thereservation to be changed or modified, such as to provide operationsimilar to that described above with respect to resource selectionprocessing at block 502. Additionally, resource reservation modificationprocessing at block 512 of embodiments may operate to verify resourceavailability with respect to the modified reservation, such as toprovide operation similar to that described above with respect toresource availability processing at block 503. Where the resource as perthe modified resource reservation remains available to the user,processing according to embodiments proceeds to block 505 for furtherprocessing as described above. It should be appreciated that, where theresource as per the modified resource reservation is not available tothe user, operation at block 512 may report the resource unavailabilityand query the user regarding selection of another resource/time for thereservation, similar to operation as described above with respect toblocks 508 and 509.

Having made a resource reservation, such as in accordance with flow 500described above, a user is preferably provided “ownership” of thereserved during the reservation period and thus is assured access to theresource as reserved. The user may access the reserved resource duringthe reservation period using a key-in process, such as described abovewith respect to flow 400 of FIG. 4. Where a user fails to key-in at areserved resource to thus initiate access thereto, embodiments mayoperate to provide signaling to remind the user of their “ownership” ofthe resource. For example, resource sever 120, upon determining that auser has not accessed a reserved resource at the beginning of areservation period, may send a message to resource key device 101 and/oruser terminal 102 to alert the user. Such a message may provide variousinformation to the user, such as to identify the reserved resource, thereservation period, the fees incurred by the user's “ownership” butnon-use of the resource, a procedure for releasing the resourcereservation should it no longer be needed or desired, etc. The user maythus proceed to access the reserved resource, release the resource foruse by others, etc. Where the user fails to take action in response tosuch a message, embodiments may operate to maintain the user's“ownership” of the resource throughout the resource reservation period,to thereby facilitate late arrivals and ensure availability to the userof the resource throughout the resource reservation period.Alternatively, embodiments may operate to release the user's “ownership”of the resource if the user fails to either access the resource orrespond to the reminder message, such as after holding the reservationopen for some threshold period of time, to thereby facilitate minimizingcharges to the user for an unused resource and to make the unusedresource available to other users of the resource utilization managementsystem.

Although the present invention and its advantages have been described indetail, it should be understood that various changes, substitutions andalterations can be made herein without departing from the spirit andscope of the invention as defined by the appended claims. Moreover, thescope of the present application is not intended to be limited to theparticular embodiments of the process, machine, manufacture, compositionof matter, means, methods and steps described in the specification. Asone of ordinary skill in the art will readily appreciate from thedisclosure of the present invention, processes, machines, manufacture,compositions of matter, means, methods, or steps, presently existing orlater to be developed that perform substantially the same function orachieve substantially the same result as the corresponding embodimentsdescribed herein may be utilized according to the present invention.Accordingly, the appended claims are intended to include within theirscope such processes, machines, manufacture, compositions of matter,means, methods, or steps.

1-29. (canceled)
 30. A method, comprising: receiving, at a resourceserver, a first request message from a first portable user device toobtain entry to a specific space resource, the request message includingdata from a first scan of a resource tag physically affixed in proximityto the specific space resource and scanned by the first portable userdevice, the request message including date and time information; inresponse to the first request message, determining, by the resourceserver, that the specific space resource is available at the requesteddate and time; reporting the availability of the specific space resourcefrom the resource server to the first portable user device; receiving,at the resource server, a confirmation message from the first portableuser device that access to the specific space resource is confirmed;receiving, at the resource server from the first portable user device,user information regarding the user of the first portable user device;at the resource server, sending an access message to the first portableuser device confirming that the specific space resource is reserved forthe first user, and to permit entry to the specific space resource; andbased on the user information, and the date and time information in thefirst request message, at the resource server, initiating a transactionto charge the user of the first portable user device for utilization ofthe accessed space resource.
 31. The method of claim 30, wherein thedata from the scanned resource tag identifies the specific spaceresource or a location of the specific space resource.
 32. The method ofclaim 31, further comprising: identifying a plurality of features of thespecific space resource based on the location of the specific spaceresource; and providing a list of the features of the specific spaceresource to the first portable user device.
 33. The method of claim 30,further comprising: in response to the first request message,determining, by the resource server, that the specific space resource isnot available at the requested date and time; and sending an accessmessage from the resource server to the first portable user deviceindicating that the specific space resource is reserved for anotheruser, and to block entry to the specific space resource.
 34. The methodof claim 30, further comprising: receiving, at a resource server, asecond request message from a second portable user device to obtainentry to the specific space resource, the second request messageincluding data from the resource tag physically affixed in proximity tothe specific space resource and scanned by the second portable userdevice, the second request message including date and time information;and transmitting, by the resource server to the second portable userdevice, a message denying access to the specific space resource whenanother user has been granted access to the specific space resource. 35.The method of claim 30, further comprising: receiving, at a resourceserver, a second request message from a second portable user device toobtain entry to the specific space resource, the second request messageincluding data from the resource tag physically affixed in proximity tothe specific space resource and scanned by the second portable userdevice, the second request message including date and time information;and when the specific space resource is configured as a shared resource,transmitting, by the resource server to the second portable user device,a message granting shared access to the specific space resource.
 36. Themethod of claim 30, the step of reporting the availability of thespecific space resource further comprising: identifying at least onenested resource associated with the specific space resource that isavailable for access.
 37. The method of claim 36, further comprising:receiving, at the resource server from the first portable user device, asecond request message to also obtain access to the nested resource; andgranting access to the nested resource when access is granted to thespecific space resource.
 38. The method of claim 30, the step ofreporting the availability of the specific space resource furthercomprising: identifying a plurality of features associated with thespecific space resource.
 39. The method of claim 38, the featuresincluding at least one equipment resource.
 40. The method of claim 38,the features including at least one of: a nested resource; a parallelresource; an alternative resource; amenities associated with thespecific space resource; available times for use of the specific spaceresource; and a pricing schedule for use of the specific resource. 41.The method of claim 30, further comprising: receiving data regardingenvironmental features of the specific space resource; and providinginstructions to the first portable user device regarding how to makeadjustments to the environmental features.
 42. The method of claim 41,wherein the environmental data includes temperature and lightingassociated with the specific space resource.
 43. The method of claim 30,the reporting step further comprising: identifying an alternative spaceresource that is available at the requested date and time when thespecific space resource is not available.
 44. The method of claim 30,the reporting step further comprising: identifying at least onedifferent date and time when the specific space resource is available.45. The method of claim 30, further comprising: receiving, at theresource server from the first portable user device, a second requestmessage including data from a second scan of the resource tag, thesecond request message indicating an exit from the specific spaceresource and terminating access to the specific space resource.
 46. Themethod of claim 30, further comprising: receiving, at the resourceserver from the first portable user device, a signal indicating an exitfrom the specific space resource and terminating access to the specificspace resource.
 47. A system, comprising: a resource server having aprocessor configured to execute instructions; and a memory coupled tothe resource server and having stored instructions that, when executedby the processor, cause the resource server to: receive a first requestmessage from a first portable user device to obtain entry to a specificspace resource, the request message including data from a resource tagphysically affixed in proximity to the specific space resource andscanned by the first portable user device, the request message includingdate and time information; in response to the first request message,determine that the specific space resource is available at the requesteddate and time; report the availability of the specific space resource tothe first portable user device; receive a confirmation message from thefirst portable user device that access to the specific space resource isconfirmed; receive user information regarding the user of the firstportable user device from the first portable user device; sending anaccess message to the controllably secured specific space resource topermit entry to the specific space resource; and based on the userinformation, and the date and time information in the first requestmessage, initiating a transaction to charge the user of the firstportable user device for utilization of the accessed space resource.